Refresh Options
Create OptionWhen
AutomaticDEMAND
The materialized view will be refreshed on demand by calling one of the three DBMS_MVIEW refresh procedures.COMMIT
A fast refresh is to occur whenever the database commits a transaction that operates on a master table of the materialized view.AUTOMATIC
The database automatically refresh the materialized view with the automatic refresh time.NEVER
The materialized view will not be refreshed with any Oracle Database refresh mechanism or packaged procedure.Start WithMethod
A datetime expression for the first automatic refresh time. Next
A datetime expression for calculating the interval between automatic refreshes.TypeFORCE
When a refresh occurs, Oracle Database will perform a fast refresh if one is possible or a complete refresh if fast refresh is not possible.FAST
A incremental refresh method, which performs the refresh according to the changes that have occurred to the master tables.COMPLETE
A complete refresh method, which is implemented by executing the defining query of the materialized view.Rollback SegmentPRIMARY KEY
A primary key materialized view. This is the default.ROW ID
A rowid materialized view.Constraint
Master
The remote rollback segment is used at the remote master site for the individual materialized view.
Local
The remote rollback segment is used for the local refresh group that contains the materialized view. This is the default.ENFORCED
Oracle Database use enforced constraints during the refresh operation.TRUSTED
Oracle Database use dimension and constraint information that has been declared trustworthy by the database administrator but that has not been validated by the database.
No index
Check this to suppress the creation of the default index.
Materialized View Options
Build Type
IMMEDIATE
The materialized view is to be populated immediately. This is the default.DEFERRED
The materialized view is to be populated by the next refresh operation.PREBUILT
To register an existing table as a preinitialized materialized view.Prebuilt Option
WITH REDUCED PRECISON
To authorize the loss of precision that will result if the precision of the table or materialized view columns do not exactly match the precision returned by subquery.WITHOUT REDUCED PRECISON
To require that the precision of the table or materialized view columns match exactly the precision returned by subquery, or the create operation will fail. This is the default.Compress
COMPRESS
Data segments are compressed to reduce disk and memory use. NOCOMPRESS
No data segments are compressed.Parallel
PARALLEL
The parallel operations will be supported for the materialized view and sets the default degree of parallelism for queries and DML on the materialized view after creation. NOPARALLEL
No parallel operations.With Degree
The default degree of parallelism for queries and DML on the materialized view after creation.Logging
LOGGING
To log the materialized view, one of its partitions, or a LOB segment.NOLOGGING
No Logging.Tablespace
Choose the tablespace in which the materialized view is to be created.Cache
CACHE
The blocks retrieved for the table are placed at the most recently used end of the least recently used (LRU) list in the buffer cache when a full table scan is performed. NOCACHE
The blocks are placed at the least recently used end of the LRU list.
For update
To allow a subquery, primary key, object, or rowid materialized view to be updated. When used in conjunction with Advanced Replication, these updates will be propagated to the master.
Enable query rewrite
To enable the materialized view for query rewrite.Physical Attributes
Set the physical attributes of the materialized view.
Using Index Clause
Tablespace
Choose the tablespace of the index.Physical Attributes
Set the physical attributes for the default index Oracle Database uses to maintain the materialized view data.